Conversation
|
Not sure who we can ping to take a look. I'm sure many users would love this feature! I noticed some errors in the build process, maybe you need to fix those? |
|
Yeah there is a typo: workdir/vector/build/generated/resolved/gplayRelease/values-pt/resolved.xml:36: Error: "radio" is a common misspelling; did you mean "rádio" ? [Typos] But I didn't changed the translations. Can I just change this word or is there some other action required? I found two bugs:
I'll try to fix this this weekend or next week. |
CHANGES.md
Outdated
| - Spaces beta | ||
|
|
||
| Improvements 🙌: | ||
| - Priority conversations for Android 11+ (#2734) |
There was a problem hiding this comment.
Change on this file is not needed anymore, can you revert please?
| @@ -0,0 +1 @@ | |||
| Priority conversations for Android 11+ | |||
|
|
||
| // We cannot use NotificationManagerCompat here. | ||
| val setting = context.getSystemService<NotificationManager>()!!.currentInterruptionFilter | ||
| val setting = context.getSystemService(NotificationManager::class.java)!!.currentInterruptionFilter |
There was a problem hiding this comment.
Not necessary but fixes some linting for me locally should i revert?
There was a problem hiding this comment.
What is the lint issue you are seeing? I do not see it, nor the CI.
The mute thing didn't appeared anymore. |
|
because of "shortcut" handling when logging out, there is a method removeAllDynamicShortcuts |
The method Also the CHANGES.md file is not OK. Is it OK for you to rebase the PR so we can have a clean history without any change on this file? |
|
|
||
| // We cannot use NotificationManagerCompat here. | ||
| val setting = context.getSystemService<NotificationManager>()!!.currentInterruptionFilter | ||
| val setting = (context.getSystemService(Context.NOTIFICATION_SERVICE) as NotificationManager).currentInterruptionFilter |
There was a problem hiding this comment.
Why not fully revert this change?
There was a problem hiding this comment.
I get a error while compiling letting it as is
26159d0 to
5bfa050
Compare
|
rebased and force pushed on my remote hope it's now better organized and implemented a function to remove all longlived shortcuts when logging out 👍 |
bmarty
left a comment
There was a problem hiding this comment.
Thanks for the update. I have one more remark, sorry I did not see it in the beginning.
| if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) { | ||
| val openRoomIntent = RoomDetailActivity.shortcutIntent(context, roomId) | ||
|
|
||
| val shortcut = ShortcutInfoCompat.Builder(context, roomId) |
There was a problem hiding this comment.
Move this code to ShortcutCreator?
There was a problem hiding this comment.
We will handle it. Thanks again for the PR!
89e82b9 to
2223e95
Compare
|
@dkter According to #1809 (comment) it doesn't support the bubble. This current PR implements it. (From what I can understand) |
@Extarys This PR doesn't implement bubbles (see the top post). It seems like it just replaces removeAllDynamicShortcuts with removeLongLivedShortcuts, and duplicates some of the code that's already in ShortcutCreator in NotificationDrawerManager (albeit not using What seems to be happening now is that shortcuts are sometimes created with the code in ShortcutCreator, and thus have correctly rendered icons, and sometimes are created with the code in NotificationDrawerManager which gives them broken icons. It looks like there's been a major refactoring of the notification code since this PR, but the redundant code still exists. |
Pull Request Checklist
Fixes #2734 partially (no bubbles)
Signed-off-by: Philipp Neumann 3daquawolf@gmail.com